Systems and methods for providing a dynamic memory bank page policy

ABSTRACT

Systems and methods for providing a dynamic memory buffer bank policy. Embodiments include a hub device for selecting a bank page policy. The hub device includes an input command stream interface and a bank page policy module. The input command stream interface detects commands from a memory controller that are directed to one or more memory devices that are connected to the hub device. The bank page policy module independently analyzes the commands to determine access patterns to the memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.

BACKGROUND OF THE INVENTION

This invention relates generally to computer memory, and more particularly to providing a dynamic memory bank page policy.

Contemporary high performance computing main memory systems are generally composed of one or more dynamic random access memory (DRAM) devices, which are connected to one or more processors via one or more memory control elements. Overall computer system performance is affected by each of the key elements of the computer structure, including the performance/structure of the processor(s), any memory cache(s), the input/output (I/O) subsystem(s), the efficiency of the memory control function(s), the main memory device(s), and the type and structure of the memory interconnect interface(s).

Extensive research and development efforts are invested by the industry, on an ongoing basis, to create improved and/or innovative solutions to maximizing overall system performance and density by improving the memory system/subsystem design and/or structure. High-availability systems present further challenges as related to overall system reliability due to customer expectations that new computer systems will markedly surpass existing systems in regard to mean-time-between-failure (MTBF), in addition to offering additional functions, increased performance, increased storage, lower operating costs, etc. Other frequent customer requirements further exacerbate the memory system design challenges, and include such items as ease of upgrade and reduced system environmental impact (such as space, power and cooling).

FIG. 1 relates to U.S. Pat. No. 5,513,135 to Dell et al., of common assignment herewith, and depicts an early synchronous memory module. The memory module depicted in FIG. 1 is a dual in-line memory module (DIMM). This module is composed of synchronous DRAMs 8, buffer devices 12, an optimized pinout, and an interconnect and capacitive decoupling method to facilitate high performance operation. The patent also describes the use of clock re-drive on the module, using such devices as phase-locked loops (PLLs).

FIG. 2 relates to U.S. Pat. No. 6,173,382 to Dell et al., of common assignment herewith, and depicts a computer system 10 which includes a synchronous memory module 220 that is directly (i.e. point-to-point) connected to a memory controller 14 via a bus 240, and which further includes logic circuitry 24 (such as an application specific integrated circuit, or “ASIC”) that buffers, registers or otherwise acts on the address, data and control information that is received from the memory controller 14. The memory module 220 can be programmed to operate in a plurality of selectable or programmable modes by way of an independent bus, such as an inter-integrated circuit I2C) control bus 34, either as part of the memory initialization process or during normal operation. When utilized in applications requiring more than a single memory module connected directly to a memory controller, the patent notes that the resulting stubs can be minimized through the use of field-effect transistor (FET) switches to electrically disconnect modules from the bus.

Relative to U.S. Pat. No. 5,513,135, U.S. Pat. No. 6,173,382 further demonstrates the capability of integrating all of the defined functions (address, command, data, presence detect, etc) into a single device. The integration of functions is a common industry practice that is enabled by technology improvements and, in this case, enables additional module density and/or functionality.

FIG. 3, from U.S. Pat. No. 6,510,100 to Grundon et al., of common assignment herewith, depicts a simplified diagram and description of a memory system 10 that includes Up to four registered DIMMs 40 on a traditional multi-drop stub bus. The subsystem includes a memory controller 20, an external clock buffer 30, registered DIMMs 40, an address bus 50, a control bus 60 and a data bus 70 with terminators 95 on the address bus 50 and the data bus 70. Although only a single memory channel is shown in FIG. 3, systems produced with these modules often included more than one discrete memory channel from the memory controller, with each of the memory channels operated singly (when a single channel was populated with modules) or in parallel (when two or more channels where populated with modules) to achieve the desired system functionality and/or performance.

FIG. 4, from U.S. Pat. No. 6,587,912 to Bonella et al., depicts a synchronous memory module 410 and system structure in which the repeater hubs 320 include local re-drive of the address, command and data to the local memory devices 301 and 302 via buses 321 and 322; generation of a local clock (as described in other figures and the patent text); and the re-driving of the appropriate memory interface signals to the next module or component in the system via bus 300.

FIG. 5 depicts a contemporary system composed of an integrated processor chip 500, which contains one or more processor elements and an integrated memory controller 510. In the configuration depicted in FIG. 5, multiple independent cascade interconnected memory busses 506 are logically aggregated together to operate in unison to support a single independent access request at a higher bandwidth with data and error detection/collection information distributed or “striped” across the parallel busses and associated devices. The memory controller 510 attaches to four narrow/high speed point-to-point memory busses 506, with each bus 506 connecting one of the several unique memory controller interface channels to a cascade interconnected memory subsystem 503 (or memory module) which includes at least a hub device 504 and one or more memory devices 509. Some systems further enable operations when a subset of the memory busses 506 are populated with memory subsystems 503. In this case, the one or more populated memory busses 508 may operate in unison to support a single access request.

FIG. 6 depicts a block diagram of a memory hub device 504 including a link interface 604 for providing the means to re-synchronize, translate and re-drive high speed memory access information to associated DRAM devices 509 and/or to re-drive the information downstream on memory bus 506 as applicable based on the memory system protocol. The information is received by the link interface 604 from an upstream memory hub device 504 or from a memory controller 510 (directly or via an upstream memory hub device 504) via the memory bus 506. The memory device data interface 615 manages the technology-specific data interface with the memory devices 509 and controls the bi-directional memory device data bus 608. The memory hub control 613 responds to access request packets by responsively driving the memory device 509 technology-specific address and control bus 614 (for memory devices in RANK0 501) or address and control bus 614′ (for memory devices in RANK1 616) and directing the read data flow 607 and write data flow 610 selectors.

The link interface 604 in FIG. 6 decodes the packets and directs the address and command information directed to the local hub device 504 to the memory hub control 613. Memory write data from the link interface 604 can be temporarily stored in the write data queue 611 or directly driven to the memory devices 509 via the write data flow selector 610 and internal bus 612, and then sent via internal bus 609 and memory device data interface 615 to memory device data bus 608. Memory read data from memory device(s) 509 can be queued in the read data queue 606 or directly transferred to the link interface 604 via internal bus 605 and read data selector 607, to be transmitted on the upstream bus 506 as a read reply packet.

In high performance memory subsystem design, there is a desire to utilize the maximum available bandwidth on the memory bus to maximize overall system performance, as well as to reduce the latency of read commands whenever possible such that any given operation can be completed in a minimum amount of time. Many methods are utilized in the industry in an attempt to achieve these goals, including the use of very high performance memory devices, the use of very wide memory busses to connect the memory devices to the memory controller, the use of one or more levels of memory caches placed as close to the processor and/or memory controller as possible, the use of either bank open or bank closed page policies based on the system design and software optimization, the use of memory pre-fetch algorithms by the memory controller, etc. While all of these methods provide varying overall system performance benefits, many can prove very costly to implement in terms of overall system cost, physical system size, system power/cooling, etc.

Current main memory system solutions may utilize a “static” (e.g. unchanging) bank page policy (either with “open” or “closed” pages) that is not changed once the system is running in a normal operating mode. In addition, the bank page policy function is implemented in the memory controller circuitry with the memory subsystem acting as a slave device responding to explicit commands from the memory controller. A further characteristic of the current approach is that memory accesses from the memory subsystem(s) are “deterministic” in nature in that the time evolution associated with each memory operation can be predicted exactly by the memory controller, which is responsible for scheduling all memory operations such that no data corruption occurs and that all memory specifications are met during normal operation.

Drawbacks to the current static approach include the fact that the hub chip cannot change its bank open/bank closed page policy when command streams are present that might better be serviced by another method. In a computer memory system, it is likely that at certain times a bank, open page policy might result in optimal performance (e.g., when memory is accessed in a sequential manner), whereas at other times a bank closed page policy might result in optimal performance (e.g., when memory is accessed in a random manner). It would be desirable to be able to dynamically switch between a bank open page policy and a bank closed page policy based on an analysis of a command stream received at a memory hub device.

BRIEF SUMMARY OF THE INVENTION

Embodiments include a hub device for selecting a bank page policy. The hub device includes an input command stream interface and a bank page policy module. The input command stream interface detects commands from a memory controller that are directed to one or more memory devices that are connected to the hub device. The bank page policy module independently analyzes the commands to determine access patterns to the memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.

Embodiments also include a method for selecting a bank page policy. The method includes detecting commands from a memory controller directed to one or more memory devices. The commands are analyzed to determine access patterns to the memory devices. The method further dynamically selects between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.

Embodiments also include a memory system including a memory controller, one or more memory devices and a memory hub device in communication with the memory controller and the memory devices. The memory hub device includes an input command stream interface for detecting commands from the memory controller directed to the memory devices. The memory hub device also includes a bank page policy module for independently analyzing the commands to determine access patterns to the memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.

Further embodiments include a memory subsystem including one or more memory device and a memory hub device. The memory hub device includes an input command stream interface for detecting commands from a memory controller directed to the memory devices. The memory hub device also includes a bank page policy module for independently analyzing the commands to determine access patterns to the memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.

Further embodiments include a memory controller for receiving and responding to memory access requests. The memory controller includes an input command stream interface for detecting commands directed to selected memory devices. The memory controller also includes a bank page policy module for independently analyzing the commands to determine access patterns to the selected memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the selected memory devices based on the analysis.

Other systems, methods, and/or computer program products according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, and/or computer program products be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings wherein like elements are numbered alike in the several FIGURES:

FIG. 1 depicts an exemplary early synchronous memory module;

FIG. 2 depicts an exemplary computer system with a fully buffered synchronous memory module that is directly connected to a memory controller;

FIG. 3 depicts an exemplary memory system, shown with a single, traditional multi-drop stub bus;

FIG. 4 depicts a fully buffered synchronous memory module and system structure, where the fully buffered synchronous memory module includes a repeater function;

FIG. 5 depicts a block diagram of a computer memory system which includes multiple independent cascade interconnect memory interface busses that operate in unison to support a single data access request;

FIG. 6 is a block diagram of an exemplary hub device in a memory subsystem;

FIG. 7 is a block diagram of an exemplary hub device including a bank page policy module that may be implemented by exemplary embodiments;

FIG. 8 depicts a process flow that may be implemented by exemplary embodiments;

FIG. 9 depicts a process flow for calculating a consecutive page access count that may be implemented by exemplary embodiments; and

FIG. 10 depicts a block diagram of system for implementing exemplary embodiments.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary embodiments increase memory performance by dynamically selecting between an open bank page policy and a closed bank page policy during runtime based on memory access requests received at a hub device from a memory controller. The memory access requests are independently analyzed at the hub device to determine the access patterns to the memory devices attached to the hub device. Based on the analysis, a bank page policy is selected for the memory devices (e.g., for all of the memory devices, for individual memory devices and/or for banks on individual memory devices). Exemplary embodiments reduce memory system inefficiencies inherent with static page policy implementations. These inefficiencies often result in added memory latency due to the need to open a page that was recently accessed and closed, or due to the need to close a page that was previously left open, to allow a different page to be accessed.

One of the key elements of a memory system design is related to the bank page policy used (bank open or bank closed). The wait time to close or to re-open a page is relatively long, and therefore, selection of a bank page policy which is inconsistent with the application command stream can result in system performance which is measurably worse than can be achieved with the use of an alternate page policy. By dynamically selecting the optimal page policy for a given command stream, the memory device address and control bus 614 614′ bandwidth requirements may be reduced due to a reduction in precharge and/or row activation command sequences that must be issued, since the memory will more often already be in the optimal state for the next access.

As used herein, the term “page” refers to a portion of a multiplexed address DRAM that is activated with the receipt of a row address. As used herein, the phrase “bank closed page policy” refers to a method of operating a memory in which the memory devices 509 are returned to a pre-charged (e.g., standby) condition upon completion of a memory operation such as a “read” or “write.” As such, the next access can be made to any address within the memory. As used herein, the phrase “bank open page policy” refers to a method of operating a memory in which the memory devices 509 are left in a state where the row address (page) remains selected. This state is also referred to as an “active/standby” state, and the memory devices 509 can be accessed upon receipt of a column address. As such, accesses can only be made to an address within the selected page, until the memory is pre-charged. As used herein, the phrase “bank open/close logical unit” (BOCLU) refers to circuitry and/or software instructions used to record the current memory bank page policy state. The circuitry and/or software instructions within the BOCLU includes counters to record the number of consecutive accesses to a page within a bank, as well as registers to record the last address accessed.

To enable a dynamic bank open/close policy, at least one BOCLU is utilized, with as many as one BOCLU per memory bank in the memory system. In exemplary embodiments with the least granularity of control, there is one general purpose BOCLU engine monitoring the address stream (or input command stream) that acts upon the entire memory subsystem 503 to which it is collected. In other exemplary embodiments, one BOCLU is utilized per memory bank, providing optimal flexibility and memory performance. In addition, some memory devices 509 in the memory subsystem 503 may have one BOCLU per memory bank, where other memory devices 509 in the same memory subsystem 503 may be monitored by one BOCLU per memory device 509. Further embodiments may include one BOCLU per memory device address and control bus 614 614′. These and other embodiments may be implemented based on the degree of granularity required in determining whether to switch between a bank open page policy and a bank closed page policy. These examples are meant to be exemplary in nature and many other combinations are possible.

FIG. 7 is a block diagram of an exemplary memory hub device 704 that may be utilized by exemplary embodiments. The hub device 704 includes an input command stream interface 706 for detecting commands from a memory controller 510 that are directed to one or more memory devices 509 that are connected to the hub device 704. The hub device 704 also includes a bank page policy module 702 (which includes one or more BOCLUs) for independently analyzing the commands to determine access patterns to the memory devices 509 and for dynamically selecting between an open bank page policy and a closed bank page policy for the selected memory devices based on the analysis.

The hub device 704 in FIG. 7 performs the same functions described above with reference to FIG. 6 along with the added function of executing a dynamic bank open/bank closed page policy. FIG. 7 depicts a bank page policy module 702 that is implemented by one or more BOCLUs for performing the memory bank page policy functions described herein. Each BOCLU corresponds to one or more memory devices 509 (all banks within each memory device 509 and/or one or more specific banks within each memory device 509). In exemplary embodiments, each BOCLU monitors an input command stream (e.g., via an input command stream interface 706 that “snoops” the input command stream for example, at the link interface 604 or the memory hub control 713) from a memory controller 510 to detect commands directed to addresses that are associated with the memory device(s) 509 corresponding to the BOCLU. When such a command is detected, the BOCLU performs an independent analysis (e.g., at the hub device 704) of the commands to determine access patterns (e.g., access is random or sequential) and then the BOCLU dynamically (during runtime) selects either an open bank page policy or a closed bank page policy for the memory devices 509 corresponding to the BOCLU. The selection is communicated to the memory hub control 713 and the memory hub control 713 applies the bank page policy when accessing the memory device(s) 509 (e.g., issues a pre-charge command when the bank page policy is a closed bank page policy).

In exemplary embodiments, each BOCLU monitors the input command stream (e.g., via an input command stream interface 706 that “snoops” the input command stream) from the memory controller 510 to detect commands directed to addresses that are associated with the memory device(s) 509 corresponding to the BOCLU. In alternate exemplary embodiments, a single input command stream interface 706 is utilized within the bank page policy module 702 to detect commands directed to addresses that are associated with all of the memory devices 509 connected to the hub device 704. The input command stream interface 706 then directs (e.g., via a multiplexer) the commands to the correct BOCLU based on the address being accessed by each command. In an exemplary embodiment, the input command stream interface 706 in the bank page policy module 702 (or within each BOCLU within the bank page policy module 702) monitors the address and command information that has been decoded by the link interface 604 as it is being transmitted to the memory hub control 713. In other exemplary embodiments, output from a module(s) located in the memory hub control 713 that is “snooping” the input command stream is utilized by the BOCLU(s). Thus, the command stream interface 706 may be located within each BOCLU in the bank page policy module 702, within the bank page policy module 702 or within the memory hub control 713.

Any number of analysis algorithms may be utilized by a BOCLU located in the bank page policy module 702 to determine whether it is advantageous to switch bank page policy modes between a “closed bank page policy” and an “open bank page policy.” Different BOCLUs within the same hub device 704 may utilize different analysis algorithms. In the minimum case, the algorithm tests whether “N” (where N is a positive integer greater than one) consecutive row accesses to the same page have occurred (or are scheduled to occur). If N is greater than or equal to two, the bank page policy would switch to a bank open page policy, as the memory system would not have to wait for the precharge time of the bank. Likewise, if N consecutive row addresses are not directed to the same page, then the bank page policy would switch to the bank closed page policy of operation. In other exemplary embodiments, the number of consecutive row addresses could be more than two prior to a bank page policy change, and could be a variable number, based on the recent history of accesses, as monitored by the BOCLU(s). Other exemplary embodiments may utilize more complicated algorithms, either by default or selectable, that use thresholds, prediction, and/or hysteresis as part of the process for determining if and when to dynamically switch the bank policy of the memory controller, hub device(s) and/or memory device(s).

In other exemplary embodiments, the dynamic bank open/closed page policy is set based on the contents of a memory command buffer, or command stack, (generally a FIFO register containing pending future commands that have been received but not yet executed), whereby the register contents are ‘snooped’ by the BOCLU or other logic in the memory hub control 713, to identify accesses to one or more pages. If any read access requests exist to a common page, then an open bank page policy is instituted for the duration of those accesses, and the accesses are re-ordered (e.g. executed in a different sequence than originally received) such that common bank accesses do not include other accesses that would require the page to be closed and re-opened to a different page, while those accesses within the page are available to be serviced. In further exemplary embodiments, accesses may not re-ordered in cases such as when one or more high priority accesses, as identified by a “tag”, pre-specified address range, access completion timer or other means, would be delayed by this action.

As is known to those skilled in the art, the re-ordering of write operations is also possible, but requires that any subsequent read accesses to the memory location(s) being written be completed subsequent to the write operation in order to maintain data integrity. When the accesses are re-ordered, exemplary embodiments include the use of “tag” bits associated with all memory read transfers to the memory controller 510, such that memory data can be returned to the memory controller 510 either earlier or later than might otherwise be expected in a conventional memory subsystem structure. In addition to other methods of correlating read access transfers to access requests, one example is the use of tag bits as described in U.S. patent application Ser. No. 11/419,586 filed on May 22, 2006 of common assignment herewith, which is hereby incorporated by reference in its entirety.

In other exemplary embodiments, the dynamic bank open/bank closed page policy is set based on a snooping (e.g., by the BOCLU or other logic in the memory hub control 713) of the input command stream, where the input command stream may or may not be stored in a memory command buffer, command stack or similar register. This solution is very similar to that of a system including a command stack, however the available commands are generally limited to recently received commands (which may be stored in received form or compressed form), the current command and possibly the next command. In this case, the analysis of the input command stream is generally historical in nature, whereas the availability of a command stack permits more accurate identification of near-term accesses.

In general, if the next access to a memory bank is for the same page, then the page should be left open, and if the next access to a memory bank is to a different page, then the page should be closed.

In further exemplary embodiments, the memory hub device 704 receives hints and/or other control information from the memory controller 510 regarding future address streams on a periodic basis. Based on this ‘hint’ information, the hub device 704 may determine an access pattern and modify the bank page policy for one or more banks. In other embodiments, the memory controller 510 notifies the hub device 704 that one or more additional commands are forthcoming (e.g. in the memory controller scheduler or buffer) that will access the same memory page. In response to the receipt of this command, the hub device 704 modifies the bank page policy (if needed) to be consistent with the information received with the current memory command, such that execution of the subsequent accesses can be optimized.

Each of these methods can be implemented without the other, or one or more may be coupled together as outlined in FIG. 8. FIG. 8 depicts a process flow that may be implemented by the bank page policy module 702 in exemplary embodiments. At block 802, the bank page policy module 702 is enabled. In exemplary embodiments, the bank page policy module processing described herein is implemented by one or more BOCLUs (e.g, one per memory bank). At block 804, the bank page policy is defaulted to a closed page policy mode. Block 806 monitors a command input stream to the memory hub device 704 (e.g., via the input command stream interface 706) to detect read and write commands to memory devices 509 attached to the memory hub device 704. Block 806 continues to monitor the input stream until a read or write command is detected. When a read or write command is detected blocks 806-818 are performed to analyze the command to determine access patterns to the memory devices 509. Based on the analysis, block 804 and/or block 818 is performed to dynamically select between an open bank policy and a closed bank page policy.

When a read or write command is detected at block 806, processing continues at block 808 to determine if another command to the same bank exists (or is being received) in the command register in the memory hub control 713. If another command to the same bank does exist, as determined at block 808, then block 810 is performed to determine if the other command to the current bank will be to the same page. If it is, then block 818 is performed and the bank policy is switched to an open bank policy, and the bank is left open upon completion of the first access. If the other command is to the same bank but does not access the same page, then the closed bank policy is retained, and the bank is closed upon completion of the current access. Processing then continues at block 804 with the closed bank policy being enabled.

If, at block 808, it is determined that another command to the same bank has not been received and/or does not exist in the hub command buffer, then a check is made at block 812 to determine if the memory controller 510 sent a hint to leave the page open or closed. If no hint was received, as determined at block 812, then block 814 is performed to utilize the current command and previous commands to determine a value for the bank page policy. A check is made at block 814 to determine if the consecutive page access count in the corresponding BOCLU is greater than or equal to a predefined threshold (e.g., 2, 4, 6). The predefined threshold may vary between BOCLUs and may be adjusted dynamically during memory subsystem operation. If the consecutive page access count is greater than or equal to the predefined threshold, then block 818 is performed and the bank page policy is switched to a bank open page policy. Processing then continues at block 806 to monitor the input command stream. If the consecutive page access count is not greater than or equal to the predefined threshold, as determined at block 814, then processing continues at block 804 with the policy continuing to be a bank closed policy. If a hint was received at block 812, then processing would continue to block 816. At block 816 a check of the memory controller hint is performed. If the hint from the memory controller requires that the page must be opened, then processing continues to block 818. If the hint requires that the page must be closed, then processing continues to block 804.

Those skilled in the art can see that the same process can be applied to a default ‘open page’ policy.

FIG. 9 depicts an exemplary process for calculating the consecutive page access count that is utilized at block 814 in FIG. 8 to determine if there is an access pattern of consecutive pages being accessed by commands in the input command stream. At block 902, the BOCLU waits for the next command. A check is made at block 904 to determine if a new command has been detected. When a new memory access (e.g. read or write) command is detected by the BOCLU, then block 906 is performed and the address (including the row (page) address) of the new access is compared to the current address (including the row address) to determine if they are equal. If the same page in memory is being accessed, then block 908 is performed and the consecutive page access count is incremented. Processing continues at block 912. If the two addresses are not equal, then block 910 is performed and the consecutive page access count is reset to zero. In alternate exemplary embodiments, the count is reset to one, is decremented, or is set to any other number. Processing continues at block 912. At block 912, the current address is recorded and processing continues at block 902 to wait for receipt of the next memory command.

In other exemplary embodiments, such as the one depicted in FIG. 10, the functions described herein are implemented in a memory controller 1002 and the setting of the bank page policy is dynamic based on the algorithms used in the memory controller 1002, and the memory controller 1002 modifies the hub operation mode by means of either commands sent to the hub over the memory bus 506, or by means of a second (lower speed) bus such as an SMBus, and I2C bus or another bus that permits communication between the memory controller 1002 and/or the integrated processor and the hub device(s) 504. FIG. 10 depicts a memory controller 1002 for receiving and responding to memory access requests. The memory controller 1002 includes an input command stream interface 1004 for detecting commands directed to selected memory devices 509. The memory controller 1002 also includes a bank page policy module 1006 for independently analyzing the commands to determine access patterns to the selected memory devices 509 and for dynamically selecting between an open bank page policy and a closed bank page policy for the selected memory devices 509 based on the analysis.

Exemplary embodiments include a computing system with a processor(s) and an I/O unit(s) (e.g., requesters) interconnected to a memory system that contains a memory controller and memory devices. In exemplary embodiments, the memory system includes a processor or memory controller interfaced to a set of hub devices (also referred to as “hub chips”). The hub devices connect and interface to the memory devices. In exemplary embodiments the computer memory system includes a physical memory array with a plurality of memory devices for storing data and instructions. These memory devices may be connected directly to the memory controller and/or indirectly coupled to the memory controller through hub devices. In exemplary embodiments, the hub-based computer memory system has memory devices attached to a communication hub device that is connected to a memory control device (e.g., a memory controller). Also in exemplary embodiments, the hub device is located on a memory module (e.g, a single substrate or physical device) that includes two or more hub devices that are cascaded interconnected to each other (and possibly to another hub device located on another memory module) via the memory bus.

Hub devices may be connected to the memory controller through a multi-drop or point-to-point bus structure (which may further include a cascade connected to one or more additional hub devices). Memory access requests are transmitted by the memory controller through the bus structure (e.g., the memory bus) to the selected hub(s). 111 response to receiving the memory access requests, the hub device translates the memory access requests to control the memory devices to store write data from the hub device or to provide read data to the hub device. Read data is encoded into one or more communication packet(s) and transmitted through the memory bus(ses) to the memory controller.

In alternate exemplary embodiments, the memory controller(s) may be integrated together with one or more processor chips and supporting logic, packaged in a discrete chip (commonly called a “northbridge” chip), included in a multi-chip carrier with the one or more processors and/or supporting logic, or packaged in various alternative forms that best match the application/environment. Any of these solutions may or may not employ one or more narrow/high speed links to connect to one or more hub chips and/or memory devices.

The memory modules may be implemented by a variety of technology including a DIMM, a single in-line memory module (SIMM) and/or other memory module or card structures. In general, a DIMM refers to a small circuit board which is comprised primarily of random access memory (RAM) integrated circuits or die on one or both sides with signal and/or power pins on both sides of the board. This can be contrasted to a SIMM which is a small circuit board or substrate composed primarily of RAM integrated circuits or die on one or both sides and single row of pins along one long edge. The DIMM depicted in FIG. 1 includes 168 pins in the exemplary embodiment, whereas subsequent DIMMs have been constructed with pincounts ranging from 100 pins to over 300 pins. In exemplary embodiments described herein, memory modules may include two or more hub devices.

In exemplary embodiments, the memory bus is constructed using multi-drop connections to hub devices on the memory modules and/or using point-to-point connections. The downstream portion of the controller interface (or memory bus), referred to as the downstream bus, may include command, address, data and other operational, initialization or status information being sent to the hub devices on the memory modules. In exemplary embodiments, the downstream memory bus connects a memory controller to a hub device, or connects a hub device to another hub device further away from the memory controller. Each hub device may simply forward the information to the subsequent hub device(s) via bypass circuitry; receive, interpret and re-drive the information if it is determined to be targeting a downstream hub device; re-drive some or all of the information without first interpreting the information to determine the intended recipient; or perform a subset or combination of these options. In exemplary embodiments, the downstream bus has a protocol that is used to control the memory system.

The upstream portion of the memory bus, referred to as the upstream bus, returns requested read data and/or error, status or other operational information, and this information may be forwarded to the subsequent hub devices via bypass circuitry; be received, interpreted and re-driven if it is determined to be targeting an upstream hub device and/or memory controller in the processor complex; be re-driven in part or in total without first interpreting the information to determine the intended recipient; or perform a subset or combination of these options. In exemplary embodiments, the upstream bus has a protocol that is used to receive responses from the memory system.

In alternate exemplary embodiments, the point-to-point bus includes a switch or bypass mechanism which results in the bus information being directed to one of two or more possible hub devices during downstream communication (communication passing from the memory controller to a hub device on a memory module), as well as directing upstream information (communication from a hub device on a memory module to the memory controller), often by way of one or more upstream hub devices. Further embodiments include the use of continuity modules, such as those recognized in the art, which, for example, can be placed between the memory controller and a first populated hub device (i.e., a hub device that is in communication with one or more memory devices), in a cascade interconnect memory system, such that any intermediate hub device positions between the memory controller and the first populated hub device include a means by which information passing between the memory controller and the first populated hub device can be received even if the one or more intermediate hub device position(s) do not include a hub device. The continuity module(s) may be installed in any module position(s), subject to any bus restrictions, including the first position (closest to the main memory controller, the last position (prior to any included termination) or any intermediate position(s). The use of continuity modules may be especially beneficial in a multi-module cascade interconnect bus structure, where an intermediate hub device on a memory module is removed and replaced by a continuity module, such that the system continues to operate after the removal of the intermediate hub device. In more common embodiments, the continuity module(s) would include either interconnect wires to transfer all required signals from the input(s) to the corresponding output(s), or be re-driven through a repeater device. The continuity module(s) might further include a non-volatile storage device (such as an EEPROM), but would not include main memory storage devices.

In exemplary embodiments, the memory system includes one or more hub devices on one or more memory modules connected to the memory controller via a cascade interconnect memory bus, however other memory structures may be implemented such as a point-to-point bus, a multi-drop memory bus or a shared bus. Depending on the signaling methods used, the target operating frequencies, space, power, cost, and other constraints, various alternate bus structures may be considered. A point-to-point bus may provide the optimal performance in systems produced with electrical interconnections, due to the reduced signal degradation that may occur as compared to bus structures having branched signal lines, switch devices, or stubs. However, when used in systems requiring communication with multiple devices or subsystems, this method will often result in significant added component cost and increased system power, and may reduce the potential memory density due to the need for intermediate buffering and/or re-drive.

Although not shown in the FIGs., the memory modules or hub devices may also include a separate bus, such as a ‘presence detect’ bus, an I2C bus and/or an SMBus which is used for one or more purposes including the determination of the hub device an/or memory module attributes (generally after power-up), the reporting of fault or status information to the system, the configuration of the hub device(s) and/or memory subsystem(s) after power-up or during normal operation or other purposes. Depending on the bus characteristics, this bus might also provide a means by which the valid completion of operations could be reported by the hub devices and/or memory module(s) to the memory controller(s), or the identification of failures occurring during the execution of the main memory controller requests.

Performances similar to those obtained from point-to-point bus structures can be obtained by adding switch devices. These and other solutions offer increased memory packaging density at lower power, while retaining many of the characteristics of a point-to-point bus. Multi-drop busses provide an alternate solution, albeit often limited to a lower operating frequency, but at a cost/performance point that may be advantageous for many applications. Optical bus solutions permit significantly increased frequency and bandwidth potential, either in point-to-point or multi-drop applications, but may incur cost and space impacts.

As used herein the term “buffer” or “buffer device” refers to a temporary storage unit (as in a computer), especially one that accepts information at one rate and delivers it at another. In exemplary embodiments, a buffer is an electronic device that provides compatibility between two signals (e.g., changing voltage levels or current capability). The term “hub” is sometimes used interchangeably with the term “buffer.” A hub is a device containing multiple ports that is connected to several other devices. A port is a portion of an interface that serves a congruent I/O functionality (e.g., a port may be utilized for sending and receiving data, address, and control information over one of the point-to-point links, or busses). A hub may be a central device that connects several systems, subsystems, or networks together. A passive hub may simply forward messages, while an active hub, or repeater, amplifies and refreshes the stream of data which otherwise would deteriorate over a distance. The term hub device, as used herein, refers to a hub chip that includes logic (hardware and/or software) for performing memory functions.

Also as used herein, the term “bus” refers to one of the sets of conductors (e.g., wires, and printed circuit board traces or connections in an integrated circuit) connecting two or more functional units in a computer. The data bus, address bus and control signals, despite their names, constitute a single bus since each are often useless without the others. A bus may include a plurality of signal lines, each signal line having two or more connection points, that form a main transmission path that electrically connects two or more transceivers, transmitters and/or receivers. The term “bus” is contrasted with the term “channel” which is often used to describe the function of a “port” as related to a memory controller in a memory system, and which may include one or more busses or sets of busses. The term “channel” as used herein refers to a port on a memory controller. Note that this term is often used in conjunction with I/O or other peripheral equipment, however the term channel has been adopted by some to describe the interface between a processor or memory controller and one of one or more memory subsystem(s).

Further, as used herein, the term “daisy chain” refers to a bus wiring structure in which, for example, device A is wired to device B, device B is wired to device C, etc. The last device is typically wired to a resistor or terminator. All devices may receive identical signals or, in contrast to a simple bus, each device may modify one or more signals before passing them on. A “cascade” or cascade interconnect’ as used herein refers to a succession of stages or units or a collection of interconnected networking devices, typically hubs, in which the hubs operate as a logical repeater, further permitting merging data to be concentrated into the existing data stream. Also as used herein, the term “point-to-point” bus and/or link refers to one or a plurality of signal lines that may each include one or more terminators. In a point-to-point bus and/or link, each signal line has two transceiver connection points, with each transceiver connection point coupled to transmitter circuitry, receiver circuitry or transceiver circuitry. A signal line refers to one or more electrical conductors or optical carriers, generally configured as a single carrier or as two or more carriers, in a twisted, parallel, or concentric arrangement, used to transport at least one logical signal.

Memory devices are generally defined as integrated circuits that are composed primarily of memory (storage) cells, such as DRAMs (Dynamic Random Access Memories), SRAMs (Static Random Access Memories), FeRAMs (Ferro-Electric RAMs), MRAMs (Magnetic Random Access Memories), Flash Memory and other forms of random access and related memories that store information in the form of electrical, optical, magnetic, biological or other means. Dynamic memory device types may include asynchronous memory devices such as FPM DRAMs (Fast Page Mode Dynamic Random Access Memories), EDO (Extended Data Out) DRAMs, BEDO (Burst EDO) DRAMs, SDR (Single Data Rate) Synchronous DRAMs, DDR (Double Data Rate) Synchronous DRAMs or any of the expected follow-on devices such as DDR2, DDR3, DDR4 and related technologies such as Graphics RAMs, Video RAMs, LP RAM (Low Power DRAMs) which are often based on the fundamental functions, features and/or interfaces found on related DRAMs.

Memory devices may be utilized in the form of chips (die) and/or single or multi-chip packages of various types and configurations. In multi-chip packages, the memory devices may be packaged with other device types such as other memory devices, logic chips, analog devices and programmable devices, and may also include passive devices such as resistors, capacitors and inductors. These packages may include an integrated heat sink or other cooling enhancements, which may be further attached to the immediate carrier or another nearby carrier or heat removal system.

Module support devices (such as buffers, hubs, hub logic chips, registers, PLL's, DLL's, non-volatile memory, etc) may be comprised of multiple separate chips and/or components, may be combined as multiple separate chips onto one or more substrates, may be combined onto a single package or even integrated onto a single device—based on technology, power, space, cost and other tradeoffs. In addition, one or more of the various passive devices such as resistors, capacitors may be integrated into the support chip packages, or into the substrate, board or raw card itself, based on technology, power, space, cost and other tradeoffs. These packages may include an integrated heat sink or other cooling enhancements, which may be further attached to the immediate carrier or another nearby carrier or heat removal system.

Memory devices, hubs, buffers, registers, clock devices, passives and other memory support devices and/or components may be attached to the memory subsystem and/or hub device via various methods including solder interconnects, conductive adhesives, socket structures, pressure contacts and other methods which enable communication between the two or more devices via electrical, optical or alternate means.

The one or more memory modules (or memory subsystems) and/or hub devices may be connected to the memory system, processor complex, computer system or other system environment via one or more methods such as soldered interconnects, connectors, pressure contacts, conductive adhesives, optical interconnects and other communication and power delivery methods. Connector systems may include mating connectors (male/female), conductive contacts and/or pins on one carrier mating with a male or female connector, optical connections, pressure contacts (often in conjunction with a retaining mechanism) and/or one or more of various other communication and power delivery methods. The interconnection(s) may be disposed along one or more edges of the memory assembly and/or placed a distance from an edge of the memory subsystem depending on such application requirements as ease-of-upgrade/repair, available space/volume, heat transfer, component size and shape and other related physical, electrical, optical, visual/physical access, etc.

As used herein, the term memory subsystem refers to, but is not limited to: one or more memory devices; one or more memory devices and associated interface and/or timing/control circuitry; and/or one or more memory devices in conjunction with a memory buffer, hub device, and/or switch. The term memory subsystem may also refer to one or more memory devices, in addition to any associated interface and/or timing/control circuitry and/or a memory buffer, hub device or switch, assembled into a substrate, a card, a module or related assembly, which may also include a connector or similar means of electrically attaching the memory subsystem with other circuitry. The memory modules described herein may also be referred to as memory subsystems because they include one or more memory devices and hub devices.

Additional functions that may reside local to the memory subsystem and/or hub device include write and/or read buffers, one or more levels of memory cache, local pre-fetch logic, data encryption/decryption, compression/decompression, protocol translation, command prioritization logic, voltage and/or level translation, error detection and/or correction circuitry, data scrubbing, local power management circuitry and/or reporting, operational and/or status registers, initialization circuitry, performance monitoring and/or control, one or more co-processors, search engine(s) and other functions that may have previously resided in other memory subsystems. By placing a function local to the memory subsystem, added performance may be obtained as related to the specific function, often while malting use of unused circuits within the subsystem.

Memory subsystem support device(s) may be directly attached to the same substrate or assembly onto which the memory device(s) are attached, or may be mounted to a separate interposer or substrate also produced using one or more of various plastic, silicon, ceramic or other materials which include electrical, optical or other communication paths to functionally interconnect the support device(s) to the memory device(s) and/or to other elements of the memory or computer system.

Information transfers (e.g. packets) along a bus, channel, link or other naming convention applied to an interconnection method may be completed using one or more of many signaling options. These signaling options may include such methods as single-ended, differential, optical or other approaches, with electrical signaling further including such methods as voltage or current signaling using either single or multi-level approaches. Signals may also be modulated using such methods as time or frequency, non-return to zero, phase shift keying, amplitude modulation and others. Voltage levels are expected to continue to decrease, with 1.5V, 1.2V, 1V and lower signal voltages expected consistent with (but often independent of) the reduced power supply voltages required for the operation of the associated integrated circuits themselves.

One or more clocking methods may be utilized within the memory subsystem and the memory system itself, including global clocking, source-synchronous clocking, encoded clocking or combinations of these and other methods. The clock signaling may be identical to that of the signal lines themselves, or may utilize one of the listed or alternate methods that is more conducive to the planned clock fiequency(ies), and the number of clocks planned within the various subsystems. A single clock may be associated with all communication to and from the memory, as well as all clocked functions within the memory subsystem, or multiple clocks may be sourced using one or more methods such as those described earlier. When multiple clocks are used, the functions within the memory subsystem may be associated with a clock that is uniquely sourced to the subsystem, or may be based on a clock that is derived from the clock related to the information being transferred to and from the memory subsystem (such as that associated with an encoded clock). Alternately, a unique clock may be used for the information transferred to the memory subsystem, and a separate clock for information sourced from one (or more) of the memory subsystems. The clocks themselves may operate at the same or fiequency multiple of the communication or functional frequency, and may be edge-aligned, center-aligned or placed in an alternate timing position relative to the data, command or address information.

Information passing to the memory subsystem(s) will generally be composed of address, command and data, as well as other signals generally associated with requesting or reporting status or error conditions, resetting the memory, completing memory or logic initialization and other functional, configuration or related information. Information passing from the memory subsystem(s) may include any or all of the information passing to the memory subsystem(s), however generally will not include address and command information. This information may be communicated using communication methods that may be consistent with normal memory device interface specifications (generally parallel in nature), the information may be encoded into a ‘packet’ structure, which may be consistent with future memory interfaces or simply developed to increase communication bandwidth and/or enable the subsystem to operate independently of the memory technology by converting the received information into the format required by the receiving device(s).

Initialization of the memory subsystem may be completed via one or more methods, based on the available interface busses, the desired initialization speed, available space, cost/complexity objectives, subsystem interconnect structures, the use of alternate processors (such as a service processor) which may be used for this and other purposes, etc. In one embodiment, the high speed bus may be used to complete the initialization of the memory subsystem(s), generally by first completing a training process to establish reliable communication, then by interrogation of the attribute or ‘presence detect’ data associated the various components and/or characteristics associated with that subsystem, and ultimately by programming the appropriate devices with information associated with the intended operation within that system. In a cascaded system, communication with the first memory subsystem would generally be established, followed by subsequent (downstream) subsystems in the sequence consistent with their position along the cascade interconnect bus.

A second initialization method would include one in which the high speed bus is operated at one frequency during the initialization process, then at a second (and generally higher) frequency during the normal operation. In this embodiment, it may be possible to initiate communication with all of the memory subsystems on the cascade interconnect bus prior to completing the interrogation and/or programming of each subsystem, due to the increased timing margins associated with the lower frequency operation.

A third initialization method might include operation of the cascade interconnect bus at the normal operational frequency(ies), while increasing the number of cycles associated with each address, command and/or data transfer. In one embodiment, a packet containing all or a portion of the address, command and/or data information might be transferred in one clock cycle during normal operation, but the same amount and/or type of information might be transferred over two, three or more cycles during initialization. This initialization process would therefore be using a form of ‘slow’ commands, rather than ‘normal’ commands, and this mode might be automatically entered at some point after power-up and/or re-start by each of the subsystems and the memory controller by way of POR (power-on-reset) logic included in each of these subsystems.

A fourth initialization method might utilize a distinct bus, such as a presence detect bus (such as the one defined in U.S. Pat. No. 5,513,135 to Dell et al., of common assignment herewith), an I2C bus (such as defined in published JEDEC standards such as the 168 Pin D1 family in publication 21-C revision 7R8) and/or the SMBUS, which has been widely utilized and documented in computer systems using such memory modules. This bus might be connected to one or more modules within a memory system in a daisy chain/cascade interconnect, multi-drop or alternate structure, providing an independent means of interrogating memory subsystems, programming each of the one or more memory subsystems to operate within the overall system environment, and adjusting the operational characteristics at other times during the normal system operation based on performance, thermal, configuration or other changes desired or detected in the system environment.

Other methods for initialization can also be used, in conjunction with or independent of those listed. The use of a separate bus, such as described in the fourth embodiment above, also offers the advantage of providing an independent means for both initialization and uses other than initialization, such as described in U.S. Pat. No. 6,381,685 to Dell et al., of common assignment herewith, including changes to the subsystem operational characteristics on-the-fly and for the reporting of and response to operational subsystem information such as utilization, temperature data, failure information or other purposes.

With improvements in lithography, better process controls, the use of materials with lower resistance, increased field sizes and other semiconductor processing improvements, increased device circuit density (often in conjunction with increased die sizes) will help facilitate increased function on integrated devices as well as the integration of functions previously implemented on separate devices. This integration will serve to improve overall performance of the intended function, as well as promote increased storage density, reduced power, reduced space requirements, lower cost and other manufacturer and customer benefits. This integration is a natural evolutionary process, and may result in the need for structural changes to the fundamental building blocks associated with systems.

The integrity of the communication path, the data storage contents and all functional operations associated with each element of a memory system or subsystem can be assured, to a high degree, with the use of one or more fault detection and/or correction methods. Any or all of the various elements may include error detection and/or correction methods such as CRC (Cyclic Redundancy Code), EDC (Error Detection and Correction), parity or other encoding/decoding methods suited for this purpose. Further reliability enhancements may include operation re-try (to overcome intermittent faults such as those associated with the transfer of information), the use of one or more alternate or replacement communication paths to replace failing paths and/or lines, complement-re-complement techniques or alternate methods used in computer, communication and related systems.

The use of bus termination, on busses as simple as point-to-point links or as complex as multi-drop structures, is becoming more common consistent with increased performance demands. A wide variety of termination methods can be identified and/or considered, and include the use of such devices as resistors, capacitors, inductors or any combination thereof, with these devices connected between the signal line and a power supply voltage or ground, a termination voltage or another signal. The termination device(s) may be part of a passive or active termination structure, and may reside in one or more positions along one or more of the signal lines, and/or as part of the transmitter and/or receiving device(s). The terminator may be selected to match the impedance of the transmission line, or selected via an alternate approach to maximize the useable frequency, operating margins and related attributes within the cost, space, power and other constraints.

Emerging high performance systems are adapting new bus structures to address some of the system cost and memory density concerns, including the use of cascade-interconnected memory subsystems that include one or more hub device(s) on a memory module. With the inclusion of the hub device(s), which can act upon command, data and address information intended for the memory devices, new solutions to maximize overall system performance can be considered. Technical effects of exemplary embodiments include reducing overall memory system latency, thereby improving system performance. In exemplary embodiments, the specific areas of improvement relate to a maximization of the utilization of the memory bus(ses) between the memory controller and the memory subsystem(s), as well as a reduction in the overall read access latency from the memory subsystem(s).

As described above, the embodiments of the invention may be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. Embodiments of the invention may also be embodied in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. The present invention can also be embodied in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.

While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. 

1. A hub device comprising: an input command stream interface for detecting commands from a memory controller directed to one or more memory devices that are connected to the hub device; and a bank page policy module for independently analyzing the commands to determine access patterns to the memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.
 2. The hub device of claim 1 wherein the access patterns are read access patterns.
 3. The hub device of claim 1 wherein the analyzing and selecting applies to one bank on one of the memory devices.
 4. The hub device of claim 1 wherein the analyzing and selecting is applied to one of the memory devices is independent of the analyzing and selecting applied to an other of the memory devices.
 5. The hub device of claim 1 wherein the analyzing and selecting is applied to one bank in one of the memory devices is independent of the analyzing and selecting applied to an other bank in the memory device.
 6. The hub device of claim 1 wherein the analyzing and selecting applies to all of the memory devices.
 7. The hub device of claim 1 wherein the commands include pending future commands located in a memory command buffer.
 8. The hub device of claim 7 wherein the bank page policy module further reorders the pending future commands in the memory command buffer to alter future access patterns.
 9. The hub device of claim 1 wherein input to the analyzing includes hints received from the memory controller.
 10. The hub device of claim 1 wherein the analyzing includes using a consecutive page access counter to select between the open bank page policy and the closed bank page policy.
 11. A method for selecting a bank page policy, the method comprising: detecting commands from a memory controller directed to one or more memory devices; analyzing the commands to determine access patterns to the memory devices; and dynamically selecting between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.
 12. The method of claim 11 further comprising selecting the closed bank page policy for the memory devices before detecting the commands.
 13. The method of claim 11 further comprising selecting the open bank page policy for the memory devices before detecting the commands.
 14. The method of claim 11 further comprising accessing a memory command buffer of pending future commands, wherein the pending future commands are input to the analyzing.
 15. The method of claim 14 further comprising reordering the pending future commands in the memory command buffer to alter future access patterns.
 16. The method of claim 11 wherein the analyzing includes selecting the open bank page policy for the memory devices if a consecutive page access count is higher than or equal to a threshold.
 17. The method of claim 11 further comprising receiving an access hint from the memory controller, wherein the access hint is input to the analyzing.
 18. The method of claim 11 wherein the access patterns are read access patterns.
 19. The method of claim 11 wherein the analyzing and selecting applies to one bank on one of the memory devices.
 20. The method of claim 11 wherein the analyzing and selecting applied to one of the memory devices is independent of the analyzing and selecting applied to an other of the memory devices.
 21. The method of claim 11 wherein the analyzing and selecting applied to one bank in one of the memory devices is independent of the analyzing and selecting applied to an other bank in the memory device.
 22. The method of claim 11 wherein the analyzing and selecting applies to all of the memory devices.
 23. The method of claim 11 wherein the detecting, selecting and analyzing are performed at a hub device.
 24. A memory system comprising: a memory controller; one or more memory devices; and a memory hub device in communication with the memory controller and the memory devices, the memory hub device comprising: an input command stream interface for detecting commands from the memory controller directed to the memory devices; and a bank page policy module for independently analyzing the commands to determine access patterns to the memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.
 25. The memory system of claim 24 wherein the analyzing and selecting applies to one bank on one of the memory devices.
 26. The memory system of claim 24 wherein the analyzing and selecting applied to one of the memory devices is independent of the analyzing and selecting applied to an other of the memory devices.
 27. The memory system of claim 24 wherein the analyzing and selecting applied to one bank in one of the memory devices is independent of the analyzing and selecting applied to an other bank in the memory device.
 28. The memory system of claim 24 wherein the analyzing and selecting applies to all of the memory devices.
 29. A memory subsystem comprising: a plurality of memory devices; and a memory hub device comprising: an input command stream interface for detecting commands from a memory controller directed to the memory devices; and a bank page policy module for independently analyzing the commands to determine access patterns to the memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the memory devices based on the analysis.
 30. The memory subsystem of claim 29 wherein the analyzing and selecting applies to one bank on one of the memory devices.
 31. The memory subsystem of claim 29 wherein the analyzing and selecting applied to one of the memory devices is independent of the analyzing and selecting applied to an other of the memory devices.
 32. The memory subsystem of claim 29 wherein the analyzing and selecting applied to one bank in one of the memory devices is independent of the analyzing and selecting applied to an other bank in the memory device.
 33. The memory subsystem of claim 29 wherein the analyzing and selecting applies to all of the memory devices.
 34. A memory controller for receiving and responding to memory access requests, the memory controller comprising: an input command stream interface for detecting commands directed to selected memory devices; and a bank page policy module for independently analyzing the commands to determine access patterns to the selected memory devices and for dynamically selecting between an open bank page policy and a closed bank page policy for the selected memory devices based on the analysis.
 35. The memory controller of claim 34 wherein the analyzing and selecting applies to one bank on one of the selected memory devices. 